build(dep): address issue with caniuse-lite causing cdai build to fail
#5816
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@matthewgallo @jlongshore seeing some tests failing here. what's the status? |
|
This is blocked because the sub dependency that Mend lists as a vulnerability ( |
|
Closing in favor of #6176 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #5815
I noticed that the v1 release has failed for the past two weeks (we need to also stop releasing v1 weekly) and it appears it is because the build script for the
cdaicomponents was failing from a warning triggered frombrowserslist.I ran the update command and confirmed that the build script for
cdaipasses locally.What did you change?
yarn.lockHow did you test and verify your work?
Ran same build script via
nx run @carbon/ibm-cloud-cognitive-cdai:buildto double check that the failing build script now passes locally.